fix: skip closed issues already fixed before installed version - #51
Merged
Merged
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✅ Files skipped from review due to trivial changes (1)
📝 WalkthroughWalkthroughThe closed-issue date filtering now adds a lower bound at Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Comment |
Previously, closed issue fetching only set an upper bound (releasedAt + 6mo) with no lower bound, pulling in issues resolved before the user's version. Now adds closed:>=releasedAt as a lower bound so only post-release fixes are included. Keeps the +6mo upper cap for old versions to bound result size.
harlan-zw
force-pushed
the
fix/skip-pre-release-closed-issues
branch
from
March 24, 2026 08:25
daebed5 to
46fe89b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🔗 Linked issue
N/A
❓ Type of change
📚 Description
Closed issue fetching previously only set an upper bound (
releasedAt + 6 months) with no lower bound, so it pulled in issues that were already resolved before the user's installed version. Now addsclosed:>=releasedAtas a lower bound, ensuring only issues closed after the release are included. For recent versions (within 6 months), all post-release closed issues are fetched. For older versions, the existing +6 month upper cap is preserved to bound result size.Summary by CodeRabbit